2013-12-16 - 6474 - Spec - SNC Based ASN to Customer #SNCProject #ShippingNotification #ABAPSNC #abapidoc
SPECIFICATIONS
6474.200 -Spec- SNC based ASN to Customer
Purpose
Generate ASN to Customer for Inbound Delivery for Drop Ship Plant
Admin Info
Purpose
|
6474.200 - Generate ASN to Customer for Inbound Delivery
|
Requested By
|
Christine DiVincenzo
|
Spec Created By
|
Vengal Rao
|
Spec Created Date
|
12/16/2013
|
Spec QA by
|
Venkat , Vengal and Siba Prasad
|
Objects
|
ZXTRKU02 , MV50AFZ1
|
Document Status
|
Complete
|
References
Prior Tickets
None
Documents
IDOC REVIEW_final.xlsx
Changes to Last Spec
A)Following changes were completed to ASN program in NECNED as per approval received from Craig on 04/14/2014.
1. Update the Header and item text in ASN Idoc with Delivery number in place of Sales order similar to Outbound.
2. Update the Inbound delivery with Planned Goods Movement date using Userexit , so that the same will be picked into ASN Inbound.
This date will be the delivery date from the PO Schedule line.
B) Following changes were completed to ASN Program before second round testing was done in NECNEQ.
1. Remove all the Extra fields populating in Inbound not in Outbound - 02/18/2014
2. Correct other fields which were marked as Under Review in First round testing. - 02/18/2014
3. Removed Extra partners ( RE, RG , LF) populating in Idoc . - 02/18/2014
4. Remove partner details of Vendor from ASN Idoc. - 02/18/2014
5. Configuration to EDI Partner - Sold To party in place of Ship To. - 02/18/2014
Functional Requirement
Currently ASNs are generated for Outbound Deliveries to Customers for orders being generated from drop ship plants.
- For Drop Ship orders from (Vendor to Customer) ASN is generated on outbound delivery document.
- The ASN is triggered to Customer on completion of Pick and PGI of Outbound.
Scope:
As part of SNC project - ASN to Customer, drop ship orders will now use Inbound deliveries instead of outbound for sending ASN to Customer (Sold To). The data send to Customer using Inbound will be same as Outbound. ASN will be send to Customer using EDI.
The control parameters used for IDOC generation used for Outbound will be used for Inbound also
Following are the control parameters:
- Basic type - /AFS/DELVRY03
- Extension - ZXDELVRY03
- Message type - DESADV
The new Condition type will be created with a new Requirement type assigned to it.
This new Requirement type is used to trigger ASN to Customer (Sold To) when PGR is completed for Inbound delivery
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
Design Strategy
The Inbound Delivery is created with reference to Purchase Order.
The strategy is to use the existing control parameters of Outbound Delivery for Inbound and using an user exit mapping of the fields will be done get the required data from the sales order via Purchase document.
Similarly in the Inbound creation program, changes to be made to incorporate the Partners from the Sales orders to be added as Partners in the header data of the Inbound delivery similar to Outbound Delivery ASN.
Configuration Change:
Following configuration has to be done to generate an ASN to Customer for Inbound
- New Condition type ZASN will be created at NACE.
- New Requirement type 903 will be assigned to the Condition type ZASN
- Sold To has been added as Partners in the delivery in the Shipping area of Config, so that ASN to triggered to Sold To .
Logic Change:
In the existing Userexit (ZXTRKU02) changes to be made to populate the missing data in the ASN for the fields given in the below table B of the technical Details Tab, similarly refer to table C also which has fields
Where excess data which is not required (currently not being populated in Outbound delivery ASN) has to be suppressed in the same userexit. Table A has fields for which values are already being populated.
Test Plan
[List test scenarios/cases to be executed here]
- Create and test Inbound deliveries and Outbound deliveries for same Customer with same materials and quantity for drop ship Plant
- o Inbound delivery the Sales order type will be TAS
- o Outbound delivery the Sales order type will be TAB.
- o Complete the packing for both deliveries with same packing information for both
- o Complete the Pick and PGI for Outbound, Putaway and PGR for Inbound
- o ASNs are generated for both the deliveries.
- Regression Test all scenarios for Inbound and outbound deliveries to ensure no impact.
Test Scenarios:
A) Basic Scenarios (similar to one from NEP)
Initial testing will be done based on below conditions -
Sl
|
Material and Grid
|
Outbound delivery from NEP
|
Inbound delivery from NECNEQ
|
Remarks
|
1
|
Single material and Grid
|
|
|
|
2
|
Multiple Materials and multiple Grids
|
|
|
|
B) Scenarios from NEP :
Sl.
|
Customer
|
Customer Name
|
Idoc No from NEP
|
Usage Type
|
Reference Outbound Delivery Number (NEP)
|
single Material/single grid
|
1
|
1004866
|
Disney Parks
|
9836884
|
|
81781988
|
Yes
|
2
|
1011257
|
Harley Davidson
|
9482233
|
|
81760892
|
|
3
|
1011257
|
Harley Davidson
|
9569546
|
Standard
|
81803532
|
|
4
|
1012507
|
Dallas
|
9489966
|
|
81733204
|
Yes
|
5
|
1012572
|
Scheels
|
9891798
|
BIN
|
81814033
|
Yes
|
6
|
1012572
|
Scheels
|
9891800
|
BIN
|
81814025
|
Yes
|
7
|
1013276
|
289C Apparel
|
9503322
|
Standard
|
81710101
|
|
8
|
1013276
|
289C Apparel
|
9610750
|
|
81749095
|
Yes
|
9
|
1007346
|
Kids Footlocker
|
9713132
|
Crossdock
|
81758225
|
|
10
|
1007346
|
Kids Footlocker
|
9713153
|
Crossdock
|
81718804
|
|
11
|
1007313
|
Champs
|
9500009
|
Crossdock
|
81708853
|
|
12
|
1007313
|
Champs
|
9713189
|
Crossdock
|
81711848
|
|
13
|
1005250
|
Major League
|
9683745
|
|
81760211
|
|
14
|
1005250
|
Major League
|
9922046
|
|
81790153
|
|
15
|
1006376
|
TSA
|
9580572
|
BIN
|
81722794
|
|
16
|
1006376
|
TSA
|
9579721
|
BIN
|
81722798
|
|
17
|
1009247
|
Nordstrom
|
9971672
|
Standard
|
81812158
|
|
18
|
1009247
|
Nordstrom
|
9971694
|
Standard
|
81812213
|
|
19
|
1007314
|
Footlocker
|
8827762
|
Caselot
|
81614821
|
Yes
|
20
|
1007314
|
Footlocker
|
8592457
|
Crossdock
|
81523820
|
Yes
|
21
|
1007314
|
Footlocker
|
9675226
|
Standard
|
81822796
|
Yes
|
22
|
1006898
|
Olympia
|
9490031
|
BIN
|
81722851
|
Yes
|
23
|
1007835
|
Dunhams
|
9489972
|
|
81735849
|
|
24
|
1009777
|
Spencer
|
9554111
|
BIN
|
81739986
|
|
25
|
1009777
|
Spencer
|
9697517
|
BIN
|
81760898
|
|
Data Analysis:
The analysis of the data was done for the below list of customers for Outbound deliveries for drop ship plant and mapped into a spreadsheet.
List of Customers
- FootLocker (Includes Eastbay/Kids/Champs)
- Major League BB Advanced Media LP
- The Sports Authority
- Nordstrom
- Disney
- Dallas
- Harley
- Scheels
- 289C Apparel LTD
- Olympia Sports
- Dunhams
- Spencer Gifts LLC
The process of analysis carried as follow:
- The list of IDOCS from NEP for above Customers for drop ship plant was collected and their data being populated was collected into a spreadsheet Segment wise.
- Similarly an Sales order with TAS was created in NECNED 300 and converted into Purchase order and then into the Inbound delivery using the Inbound program
- Packing was done manually to Inbound similar to the one being done for outbound delivery and PGR was triggered.
- ASN triggered to the Customer automatically through IDOC
The table displays the number of fields being currently populated in Outbound and Inbound and also the(In Outbound and not in Inbound):
Name of Segment
|
Outbound Delivery – fields with values populated
|
Inbound delivery – Field with values populated
|
In Outbound Delivery –
not in Inbound
|
E1EDL20 : Delivery header
|
14
|
14
|
0
|
E1EDL22 : Delivery Header Descriptions
|
5
|
5
|
0
|
E1EDL21 : Delivery Header Additional Data
|
4
|
4
|
0
|
E1EDL23 : Deliv.Header Addit.Data Descriptions
|
4
|
4
|
0
|
E1ADRM1 : Central Address Segment Group, Main Segment
|
11
|
11
|
0
|
E1ADRE1 : Central Address Segment Group, Additional Data Segment
|
2
|
2
|
0
|
E1EDT13 : IDoc: Deadline (delivery)
|
9
|
9
|
0
|
E1TXTH8 : General Text Header
|
5
|
5
|
0
|
E1TXTP8 : General Text Segment
|
2
|
2
|
0
|
E1EDL28 : Routes
|
3
|
3
|
0
|
E1EDL29 : Routes Descriptions
|
2
|
2
|
0
|
E1EDL24 : Delivery Item
|
37
|
37
|
0
|
Z1REFORDP01 : New Era Reference Order Information
|
21
|
21
|
0
|
/AFS/E1EDL24 : AFS IDoc: Additional data for delivery item
|
4
|
4
|
0
|
/AFS/E1J3AKG : AFS IDoc: Additional customer groups
|
8
|
8
|
0
|
E1J3AI2 : AFS IDOC: Reference data on item level
|
4
|
4
|
0
|
E1J3AI2 : AFS IDOC: Reference data on item level
|
3
|
2
|
1
|
E1J3AIM : AFS IDOC: Doc. item object identification
|
4
|
4
|
0
|
E1J3AIT : AFS IDoc: VAS Ticketing / Labelling
|
3
|
3
|
0
|
E1J3AIP : AFS IDoc: VAS Packing
|
3
|
3
|
0
|
E1J3AIS : AFS IDoc: VAS Special Services
|
6
|
6
|
0
|
E1EDL25 : Delivery Item Descriptions
|
8
|
8
|
0
|
E1EDL26 : Delivery Item Additional Data
|
15
|
14
|
1
|
E1EDL27 : Delivery Item Additional Data Descriptions
|
9
|
9
|
0
|
E1EDL35 : Export Data Delivery Item
|
1
|
1
|
0
|
E1EDL36 : Export Data Delivery Item Descriptions
|
1
|
1
|
0
|
E1EDL43 : IDoc: Reference
|
4
|
4
|
0
|
E1EDL41 : Reference data ordering party
|
6
|
3
|
3
|
E1EDL42 : Reference data ordering party texts
|
1
|
0
|
1
|
E1TXTH9 : General Text Header
|
5
|
5
|
0
|
E1TXTP9 : General Text Segment
|
2
|
2
|
0
|
E1EDL12 : IDOC: Configuration
|
6
|
6
|
0
|
E1EDL37 : Handling unit header
|
28
|
28
|
|
E1EDL38 : Handling Unit Header Descriptions
|
3
|
3
|
0
|
E1EDL44 : IDoc: Handling Unit Item (Delivery)
|
14
|
12
|
2
|
Z1MATL44 : New Era: Extended Material Information
|
8
|
8
|
0
|
Grand Total
|
265
|
257
|
8
|
Limitations:
Below are fields in the segments where values will not populate for Inbound (Refer above table - last column )depending upon the condition stated below.
Segment
|
Field
|
Description
|
Populated data
|
Remarks
|
E1EDL26
|
SOBKZ
|
Special Stock Indicator
|
E
|
This is relevant only if stock is shipped out of NEC warehousing using TAB orders
|
E1EDL41
|
BSARK
|
Customer purchase order type
|
EDI
|
only get populated for EDI orders
|
|
IHREZ
|
Your Reference
|
User defined value
|
only get populated for EDI orders
|
|
POSEX
|
Item Number of the Underlying Purchase Order
|
User defined value
|
only get populated for EDI orders
|
E1EDL42
|
BSARK_BEZ
|
Description of purchase order type
|
EDI
|
only get populated for EDI orders
|
E1EDL44
|
SOBKZ
|
Special Stock Indicator
|
E
|
This is relevant only if stock is shipped out of NEC warehousing using TAB orders
|
|
SONUM
|
Special Stock Number
|
System generated number
|
This is relevant only if stock is shipped out of NEC warehousing using TAB orders
|
E1J3AI2
|
J_APOSNR
|
Item number
|
User defined value
|
only get populated for EDI orders
|
Solution Details
[Provide complete technical details for configuration or programming here]
Issues
None
- 2014-01-30 - 6474 - Rel Notes - SNC Configuration to get Receiving plant in Inbound delivery
- 2014-01-30 - 6474 - Rel Notes - SNC Enhancement to get sales order details in Inbound delivery
- 2014-01-30 - 6474 - Rel Notes - SNC Enhancement to get data into ASN Idoc for Inbound similar to outbound ASN
- vengal - 2014-01-28 - 6474.200 - Spec - SNC Inbound delivery Enhancement
- 2014-03-13 - 6474 - Rel Notes - SNC Enhancement to get data into ASN Idoc for Inbound similar to outbound
- 2014-03-13 - 6474 - Rel Notes - EDI Partner(SP) Configuration for ASN Inbound IDoc